System and method for determining productivity of a drilling project

ABSTRACT

Drilling machine data is received during execution a plurality of processes by a drilling machine associated with each of a plurality of phases of a drilling project. Processing includes automatically detecting a start state and an end state of each of the phases, generating time stamp data in response to detecting at least the start state of each phase, receiving an operator input confirming the start state of a particular phase of the plurality of phases, and electronically identifying the particular phase based on the operator input. Processing also includes storing the identity, a time duration, and the machine data for each of the particular and preceding phases, and generating an output comprising the identity, a time duration, and the machine data for each of the phases.

SUMMARY

Embodiments are directed to a method for use by a drilling machinecomprising receiving drilling machine data during execution a pluralityof processes by the drilling machine associated with each of a pluralityof phases of a drilling project. The method comprises automaticallydetecting a start state and an end state of each of the phases,generating time stamp data in response to detecting at least the startstate of each phase, receiving an operator input confirming the startstate of a particular phase of the plurality of phases, andelectronically identifying the particular phase based on the operatorinput. The method also comprises storing the identity, a time duration,and the machine data for each of the particular and preceding phases,and generating an output comprising the identity, a time duration, andthe machine data for each of the phases.

Some embodiments are directed to a method for use by a drilling machinecomprising receiving drilling machine data during execution a pluralityof processes by the drilling machine associated with each of a pluralityof phases of a drilling project. The method comprises automaticallydetecting a start state and an end state of each of the phases,generating time stamp data in response to detecting at least the startstate of each phase, receiving an operator input confirming the startstate of a particular phase of the plurality of phases, andelectronically identifying the particular phase and one or more phasespreceding the particular phase based on the operator input. The methodalso comprises storing the identity, a time duration, and the machinedata for each of the particular and preceding phases, and generating anoutput comprising the identity, a time duration, and the machine datafor each of the phases.

Other embodiments are directed to a method for use with a drillingmachine comprising receiving data about the drilling machine during aplurality of processes associated with each of a plurality ofnon-excavation phases of a drilling project. The method comprisesautomatically detecting a start state and an end state of each of thephases, generating time stamp data in response to detecting at least thestart state of each phase, receiving an operator input confirming thestart state of a particular phase of the plurality of phases, andelectronically identifying the particular phase based on the operatorinput. The method also comprises storing the identity, a time duration,and the machine data for the particular phase, and generating an outputcomprising the identity, time duration, and machine data for theparticular phase.

Further embodiments are directed to an apparatus for use with a drillingmachine comprising a processor, a memory, a timer device, a statedetector, and a user interface. The processor is configured to receivedrilling machine data during execution of each of a plurality of phasesof a drilling project, cooperate with the state detector toautomatically detect a start state and an end state of each of thephases, and cooperate with the timer device to determine a time durationof each phase. The processor is also configured to cooperate with theuser interface to receive an operator input confirming the start stateof a particular phase of the plurality of phases, and electronicallyidentify the particular phase and one or more phases preceding theparticular phase based on the operator input. The processor is furtherconfigured to store the identity, a time duration, and the machine datafor each of the particular and preceding phases in the memory, andgenerate an output comprising the identity, a time duration, and themachine data for each of the phases.

The above summary is not intended to describe each disclosed embodimentor every implementation of the present disclosure. The figures and thedetailed description below more particularly exemplify illustrativeembodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a horizontal directional drilling (HDD) machine withwhich embodiments of the disclosure can be implemented;

FIG. 2 illustrates various processes for automatically identifying andacquiring data for phase-specific processes performed by an HDD machinein accordance with various embodiments;

FIG. 3 illustrates various processes for automatically identifying andacquiring data for phase-specific processes performed by an HDD machinein accordance with various embodiments;

FIG. 4 illustrates various processes for automatically identifying andacquiring data for phase-specific processes performed by an HDD machinein accordance with various embodiments;

FIG. 5 illustrates various processes for automatically identifying andacquiring data for phase-specific processes performed by an HDD machinein accordance with various embodiments;

FIG. 6 illustrates various processes for automatically identifying andacquiring data for phase-specific processes performed by an HDD machinein accordance with various embodiments;

FIG. 7 illustrates various processes for automatically identifying andacquiring data for phase-specific processes performed by an HDD machinein accordance with various embodiments;

FIG. 8 illustrates various processes for automatically identifying andacquiring data for phase-specific processes performed by an HDD machinein accordance with various embodiments;

FIG. 9 illustrates various processes for automatically identifying andacquiring data for phase-specific processes performed by an HDD machinein accordance with various embodiments;

FIG. 10 is a block diagram of an apparatus for automatically identifyingand acquiring data for phase-specific processes performed by an HDDmachine in accordance with various embodiments;

FIG. 11 illustrates a project manifest implemented as a relationaldatabase in accordance with various embodiments;

FIG. 12 illustrates various components of a system for automaticallytallying drill rods of a drill string and for automatically identifyingand acquiring data for boring phase processes performed by a drillingmachine in accordance with various embodiments; and

FIG. 13 is a block diagram of various components of a system foraccurately tallying drill rods added to and removed from a drill stringin accordance with various embodiments of the disclosure.

The figures are not necessarily to scale. Like numbers used in thefigures refer to like components. However, it will be understood thatthe use of a number to refer to a component in a given figure is notintended to limit the component in another figure labeled with the samenumber.

DETAILED DESCRIPTION

In the following description of the illustrated embodiments, referencesare made to the accompanying drawings forming a part hereof, and inwhich are shown by way of illustration, various embodiments by which theinvention may be practiced. It is to be understood that otherembodiments may be utilized, and structural and functional changes maybe made without departing from the scope of the present invention.

Systems, devices or methods according to the present invention mayinclude one or more of the features, structures, methods, orcombinations thereof described herein. For example, a device or systemmay be implemented to include one or more of the advantageous featuresand/or processes described below. It is intended that such a device orsystem need not include all of the features described herein, but may beimplemented to include selected features that provide for usefulstructures, systems, and/or functionality.

Embodiments are directed to systems and methods for determining overallproductivity of a drilling project that involves a multiplicity ofdiscrete phases. Embodiments are directed to systems and methods forincreasing the accuracy of drilling project productivity computations byinfrequently querying a drilling machine operator to confirm the stateof one or more phases of a drilling project. Embodiments are directed tosystems and methods for infrequently querying a drilling machineoperator or other authorized person to confirm the state of one or morephases of a drilling project via operator input, and correctlyidentifying and producing productivity computations for one or moredrilling project phases that precede the phase as confirmed by theoperator input. The operator may be located at or remote from thedrilling machine when providing an input to confirm the state of one ormore phases of a drilling project. For example, the drilling machineoperator may be considered a remotely located person, such as a locatoroperator or a site supervisor, who operates a user interface device thatcommunicatively couples to the drilling machine.

Embodiments of the disclosure are generally directed to drillingprojects, such as those involving horizontal and/or vertical drilling.Various embodiments of the disclosure are directed to horizontaldirectional drilling, which is understood by those of ordinary skill inthe drilling industry as involving directional drilling of relativelyshallow and predominantly horizontal bores through the earth, such asfor running utilities under a streets and rivers, for example. Variousembodiments are directed to vertical drilling, which is understood bythose of ordinary skill in the drilling industry to involve drilling ofrelatively deep and predominantly vertical bores in the earth. Althoughthe present disclosure describes various methodologies in the context ofhorizontal directional drilling, it is understood that the disclosedmethodologies may be applied in the context of vertical drillingmachines, including those with a directional (i.e., steering)capability.

FIG. 1 illustrates a horizontal directional drilling machine 100, inaccordance with various embodiments. The drilling machine 100, shown inFIG. 1, includes a propulsion apparatus 123 coupled to a drill rodmanipulation apparatus 121. The propulsion apparatus 123 includes anengine 106 and one or more hydraulic pumps 117 supported by a chassis102. A track drive 119 or other drive arrangement allows the drillingmachine 100 to be maneuvered around the worksite. The drill rodmanipulation apparatus 121 includes a rack 110, a carriage 116, and avise arrangement 115. The carriage 116 is configured for longitudinaldisplacement along the rack 110 and can travel longitudinally between arear position, nearest the chassis 102, and a front position, nearestthe vise arrangement 115. The carriage 116 supports a gearbox 108, whichincludes a rotary drive 154 configured to rotatably couple and decoupleto and from a drill rod 114. The gearbox 108 and rotary drive 154 travellongitudinally with the carriage 116 along the rack 110. The gearbox 108supports or is coupled to a rotation motor 111 and a displacement motor113. In some embodiments, the rotation and displacement motors 111 and113 are hydraulic motors. Other embodiments may utilize electric motorsrather than, or in addition to, hydraulic motors. Other modes ofpropulsion are contemplated.

Operation of the rotation and displacement motors 111 and 113 ismonitored using one or more sensors, respectively, such as pressuretransducers. In some embodiments, the rotary drive of the gearbox 108 ismonitored using one or more pressure transducers 122. The longitudinaldisplacement of the gearbox 108 is monitored by one or more positionssensors 120, 126 and/or a rotary encoder 124 provided on a pinion gear.A pressure transducer 122, torque transducer 128 or other sensor (orcombination of sensors) provides an indication of torque produced by therotary drive 154 of the gearbox 108. It is understood that one or moresensors can be used to measure torque directly or indirectly (e.g., asensor that senses a parameter like fluid pressure that can becorrelated to torque). In some embodiments, one or more torquethresholds or limits can be established for purposes of determiningoccurrence of drill rod addition and removal events and for purposes ofproviding an accurate tally of drill rods added to and removed from adrill string 112, in accordance with various embodiments, as iscoordinated by a controller 101 of the drilling machine 100. Thecontroller 101 is configured to execute one or more algorithms forautomatically identifying and acquiring data for phase-specificprocesses performed by the drilling machine 100 in accordance withvarious embodiments.

There are consistent aspects of workflow associated with HDD projects,including processes that occur during discrete phases of an HDD projectsuch as a set-up and transport phase before machine operation starts,during a machine operation phase, and during a teardown phase, aftermachine operation is finished. The overall productivity of a crew istypically evaluated on the basis of productivity during all of thesephases.

During setup, transport, and teardown phases, for example, the HDDmachine may not be directly involved in activities. However, monitoringprocess attributes of the HDD machine during these processes enableinsight into the overall productivity related to that specific HDDproject. During the drilling machine operation phase, monitoring processattributes of the HDD machine enable insight into productivity duringmachine operation.

Some crews attempt to document notes including observations ofactivities that occurred during specific projects, or during a specificday, that impact productivity. However, these notes are often made atthe end of the day, after some time has passed. Thus, the accuracy ofthese notes is sometimes not as reliable as desired, and the amount ofdata is limited.

Embodiments of the disclosure are directed to a system that includes anHDD machine with a control and data logging system, combined with anoperator interface that requires minimal operator input to confirmsuspected operating states. From the operator input, the control systemcan process logged data to derive attributes of processes that haveoccurred previously, and that are associated with a specific HDDproject. The resulting derived attributes and machine information can begenerated and displayed to the operator and supervisors while theproject is in-process, and can be compiled into a digital summaryreport, or manifest, for that specific project, for review during thephase and for review when the project is completed.

Embodiments are directed to a component of an HDD machine that iscapable of automatically identifying phase-specific process attributesfor an HDD project including processes that occur while the HDD machineis being operated to perform a boring operation, and also processes thatoccur before the boring operation has started at the specific location,for that specific project, and after the boring operation is finishedfor that specific project. Attributes of a process typically include theduration of each process and machine parameters associated with thatprocess.

Various embodiments are described using the following terms, which aredefined below and are applicable in certain, but not necessarily all,contexts. The term “HDD project” refers to a drilling project thatinvolves a multiplicity of discrete project phases. The term“phase-specific” refers to operations that are related to a specificphase of an HDD project. The term “automatic” or “automatically” refersto a process wherein at least some actions occur without operatorinteraction, thus the term is used herein to describe a process whereminimal or no operator interaction is required. The term “processattributes” refers to information about a specific process of a givenphase, and can be derived from data measured during the execution of theprocess and possibly other data. The term “process” refers to a stepthat is a routine part of completing a specific project.

Embodiments of the disclosure are directed to a system that includes amachine state detection algorithm for an HDD machine, to enable themachine to recognize specific states of operation. That data can becombined with time stamp and data logging, in a temporary cache ofmemory for example. Other attributes, in addition to the time stamps,can be recorded in a temporary cache of memory, as a function of themachine state.

Turning now to FIG. 2, there is illustrated various processes forautomatically identifying and acquiring data for phase-specificprocesses performed by an HDD machine in accordance with variousembodiments. According to the embodiment shown in FIG. 2, a methodinvolves operating 20 an HDD machine during a multiplicity of phases ofan HDD project. The method involves detecting 22 a suspect phase of themultiplicity of phases. A suspect phase is generally one in whichlimited information is known about the phase or one in which otherphases rely on knowing additional information about the suspect phase. Atypical suspect phase is one in which information currently available tothe HDD machine is insufficient for the HDD machine to correctlyidentify the phase within an acceptable degree of accuracy (e.g., alikelihood of correctly identifying the phase is >92%). In response todetecting a suspect phase, an operator prompt is generated 24 requestingconfirmation of the suspect phase. In response to the operator prompt,an input from the operator is received 26 confirming the suspect phase.After receiving operator confirmation of the suspect phase, productivitydata is produced 28 for the suspect phase. Various types of output canbe generated 29 for the suspect phase.

FIG. 3 illustrates various processes for automatically identifying andacquiring data for phase-specific processes performed by an HDD machinein accordance with various embodiments. The method shown in FIG. 3involves operating 30 an HDD machine during a multiplicity of phases ofan HDD project, and detecting 32 a suspect phase of the multiplicity ofphases. In response to detecting the suspect phase, an operator promptrequesting confirmation of the suspect phase is generated 34. The methodalso involves receiving 36 an input from the operator confirming thesuspect phase, and producing 38 productivity data for the suspect phase.The method further involves identifying 40 one or more phases precedingthe suspect phase based in part on the operator input, and producing 42productivity data for each of the preceding phases. The method generallyinvolves generating 44 various types of output data for the suspectphase and preceding phases.

FIG. 4 illustrates various processes for automatically identifying andacquiring data for phase-specific processes performed by an HDD machinein accordance with various embodiments. The method shown in FIG. 4involves operating 402 an HDD machine during a multiplicity of phases ofan HDD project, and generating 404 an operator prompt about a particularphase. The method also involves receiving 406 from the operator an inputconfirming a state of the particular phase, and electronicallyidentifying 408 the particular phase based on the operator input. Themethod further involves storing 410 the identity and information aboutthe particular phase, and generating 412 an output comprising theidentity and information about the particular phase.

The method illustrated in FIG. 5 involves many of the processes shown inFIG. 4 along with additional processes according to various embodiments.The method shown in FIG. 5 involves operating 502 an HDD machine duringa multiplicity of phases of an HDD project, generating 504 an operatorprompt about a particular phase, receiving 506 from the operator aninput confirming a state of the particular phase, and electronicallyidentifying 508 the particular phase based on the operator input. Themethod shown in FIG. 5 also involves electronically identifying 510 oneor more phases preceding the particular phase based on the operatorinput, and storing 512 the identity and information about the particularphase and the preceding phases. The method further involves generating514 output comprising the identities and information about theparticular phase and the preceding phases.

The embodiment of the method illustrated in FIG. 6 involves many of theprocesses shown in FIG. 4 along with additional processes. The methodshown in FIG. 6 involves operating 602 an HDD machine during amultiplicity of phases of an HDD project, generating 604 an operatorprompt about a particular phase, receiving 606 from the operator aninput confirming a state of the particular phase, and electronicallyidentifying 608 the particular phase based on the operator input. Themethod shown in FIG. 6 also involves determining 610 a duration of timeto complete a particular phase, and storing 612 the identity, durationof time, and information about the particular phase. The method alsoinvolves generating 614 output comprising the identity, time duration,and information about the particular phase.

The method shown in FIG. 7 involves many of the processes shown in FIG.5 along with additional processes. The method shown in FIG. 7 involvesoperating 702 an HDD machine during a multiplicity of phases of an HDDproject, generating 704 an operator prompt about a particular phase,receiving 706 from the operator an input confirming a state of theparticular phase, and electronically identifying 708 the particularphase based on the operator input. The method shown in FIG. 7 alsoinvolves electronically identifying 710 one or more phases preceding theparticular phase based on the operator input, and determining 712 aduration of time to complete the particular phase and the precedingphases based in part on the operator input. The method further involvesstoring 714 the identity, time duration, and information about theparticular phase of the preceding phases, and generating 716 outputcomprising the identities, time durations, and information about theparticular phase in the preceding phases.

FIG. 8 illustrates an embodiment of a method for automaticallyidentifying and acquiring data for phase-specific processes performed byan HDD machine in accordance with various embodiments. The method shownin FIG. 8 involves performing 902 a multiplicity of HDD machineprocesses for a multiplicity of phases of an HDD project, and producingor receiving 804 HDD machine data during execution of the processes. Themethod also involves automatically detecting 806 a start state and anend state of each of the phases, and generating 808 time stamp data inresponse to detecting at least the start state of each phase. The methodalso involves receiving 810 an operator input confirming the start stateof a particular phase of the plurality of phases, electronicallyidentifying 812 the particular phase based on the operator input, andstoring 814 the identity, time duration, and machine data for theparticular phase. The method further involves generating 816 outputcomprising the identity, time duration, and machine data for theparticular phase.

FIG. 9 illustrates an embodiment which involves many the processes shownin FIG. 8 in accordance with various embodiments. The method shown inFIG. 9 involves performing 902 a multiplicity of HDD machine processesfor a multiplicity of phases of an HDD project, producing or receiving904 HDD machine data during execution of the processes, automaticallydetecting 906 a start state and an end state of each of the phases, andgenerating 908 time stamp data in response to detecting at least thestart state of each phase. The method also involves receiving 910 anoperator input confirming the start state of a particular phase of theplurality of phases and electronically identifying 912 the particularphase based on the operator input. The method further involveselectronically identifying 914 one or more preceding phases based inpart on the operator input, storing 916 the identities, time durations,and machine data for the particular phase and the preceding phases, andgenerating 918 output comprising the identities, time durations, andmachine data for the respective phases.

FIG. 10 is a block diagram of an apparatus for automatically identifyingand acquiring data for phase-specific processes performed by an HDDmachine in accordance with various embodiments. The apparatus shown inFIG. 10 includes an HDD machine 105 which comprises a number ofcomponents, including those described previously with reference to FIG.1 including various sensors 109. The HDD machine 105 includes aprocessor 101 which is coupled to a memory 162, a timestamp generator166 (or other type of timer device), a state detector 164, and a userinterface 160. The processor 101 receives various forms of HDD machinedata from the HDD machine 105. The state detector 164 is configured todetermine the state of HDD project phases, such as a start state and/orand end state of each phase. According to some embodiments, the memory162 is configured to store a project manifest 168, which includesinformation associated with each phase of a multiplicity of phases of anHDD project executed by the HDD machine 105.

In the representative embodiment shown in FIG. 10, the HDD machine 105is configured to perform processes during a number of different phasesof an HDD project. According to various embodiments, the differentphases of an HDD project can include one or more of a transport phase180, a set-up phase and 82, a boring phase 184, a pullback/reaming phase186, and a breakdown phase 188. It is noted that each of these phasescan include one or more sub-phases. The following table illustratesvarious processes associated with a number of different phases of an HDDproject. Each of the phases is associated with various HDD machineinputs or actions, some of which may involve an operator. Therepresentative list of steps or processes in Table 1 may be tracked fora specific phase, along with some considerations for inputs or actionsof a drilling machine that may be useful to determine the machine isperforming that step.

TABLE 1 Phase Inputs/Actions Transport Using telematics GPS bread crumbsMachine in certain position Machine in a constant RPM Machine TrackingTracks moving - speed, pressure spikes Stake downs up Outrigger upOperator out of the seat Use of rack tilt to help with break over pointUsing a remote (tracking speed) Location vs. how long it was trackedMachine Warm Up Machine idle - no hydraulic Machine Set up Rack Tiltgoes down Stake downs moving - not always used Outrigger moving - notalways used Water Pressure - mud inlet sensor - many run dry Locator andsonde synced up Recording locator/sonde calibration event Tooling setup - drill head is on and front vice closed Machine Pilot Boring RodCount begins Generate Operator Carriage and vice sequence occurringPrompt After 2 rod counts query operator Receive Operator Input “Are youdrilling?” Implement Phase Set a time stamp. Identification ProcedureRack tilt Operator in seat Swab Sequence Time per Rod Abnormalities RodCounting not happening Carriage not moving Vices not moving Operator outof seat - How long? Rack tilt angle change Low inlet mud pressureMachine Fault Codes Thrust circuit failure, etc. Pressure Changes overthe length of the borepath Hydraulic spike signatures Pullback/ReamingRod Count Generate Operator Vices and carriage movement Prompt QueryOperator “Are you pulling back?” Receive Operator Input Count get to “0”Implement Phase Query Operator “Bore complete?” Identification ProcedureMachine Tracking with GPS location product Stake downs up Outriggers upRack moved slightly

FIG. 10 further shows a sequence 190 of phases of an HDD projectorganized in chronological order of occurrence for illustrativepurposes. The beginning and end of each discrete phase 192 of thesequence 190 of phases is denoted by a state change, Sn. Detecting astate change, Sn, typically involves detecting one or both of a startstate and an end state for each phase by the state detector 164. Aduration of time, t_(n), for each phase 192 is computed for each phase192. The duration of time, t_(n), for each phase 192 can be computed asthe total amount of time that has elapsed between start and end statesof each phase 192. In some embodiments, the duration of time, t_(n), fora particular phase 192 can be computed as the total amount of time thathas elapsed between the end state of the immediately preceding phase andthe end state of the particular phase 192. The time stamp generator 166can be configured to generate timestamps at each of the state changes toallow for computation of the elapsed time for each phase. The time stampgenerator 166 can also be configured to generate timestamps at each ofstate change of one or more sub-phases of a particular phase, to allowfor computation of the elapsed time for each sub-phase. In someembodiments, a timer device can be used as a time stamp generator 166and configured to directly provide the elapsed time for each particularphase.

In general, detecting one or both of a start state and an end state of aparticular phase or sub-phase by the state detector 164 involvesanalyzing signals or data received from one or more sensors of the HDDmachine. In some embodiments, detecting one or both of a start state andan end state of a particular phase or sub-phase involves analyzingsignals transmitted over a network or communication bus of the HDDmachine 105. Analyzing network or communication bus traffic generallyreduces the number of sensors required to determine (e.g., discriminatebetween) state changes of the various phases or sub-phases, such as byanalyzing control signals in addition to sensor signals communicatedover the network or communication bus of the HDD machine 105.

With continued reference to FIG. 10, six discrete phases 192 of an HDDproject are shown, with each phase having its associated processes thatare performed by the HDD machine 105. In FIG. 10, phase n−3 is theearliest phase 192 to occur in time of the sequence 190 of phases, andphase n+2 is the last phase 192 of the sequence 190 to occur. The statedetector 164 is configured to detect a change in state, Sn−3, as thebeginning of phase n−3 and a subsequent change in state, Sn−2, as theend of phase n−3. In some embodiments, each phase can have its own startstate and its own end state, with the beginning and ending of aparticular phase defined by the start and end states of the particularphase.

During the time duration, t_(n)−3, of phase n−3, the processor 101acquires HDD machine data from the HDD machine 105 and temporarilystores the machine data, the time duration data, and a phase ID code foridentifying phase n−3 in a cache memory 163 (e.g., temporary memory). Insome embodiments, various attributes of the data acquired during phasen−3 can be calculated based on the various data acquired during phasen−3 (and possibly other data). For example, the derived attributescalculated for phase n−3 can represent information about specificprocesses performed during phase n−3 that can be derived from datameasured during execution of these processes.

In response to detecting the end state for phase n−3 (e.g., completionof phase n−3), such as by the state detector 164 detecting the statechange Sn−2, the processor 101 coordinates the transfer of data forphase n−3 from the cache memory 163 to archive memory (e.g., permanentmemory), such as memory 162. According to some embodiments, the dataacquired and, optionally, computed during phase n−3 is stored in aproject manifest 168 in archive memory 162. For example, the projectmanifest 168 can be configured as a relational database in the memory162. The project manifest 168 can include all phase-related data for agiven HDD project, with individual fields being populated by variousforms of data associated with each phase. For example, the phase-relateddata stored in the project manifest 168 can include an ID code, timedata, machine data, and derived attributes for each phase stored in theproject manifest 168. Moreover, such data acquired for each sub-phase ofa given project phase can also be stored in the relational database ofthe project manifest 168. In this way, data can be analyzed for amultiplicity of sub-phases and phases to glean information about overallHDD project productivity and efficiency. FIG. 11 illustrates a projectmanifest 168 implemented as a relational database in accordance withvarious embodiments. The project manifest 168 includes a number of datafields including project name, phase, ID code, sub-phase, total time,machine data, and derived attributes. It is understood that other and/oradditional information fields can be included within the projectmanifest 168.

In the illustrative example shown in FIG. 10, the HDD machine 105executes three phases for which data is collected and transferred tomemory in the manner discussed hereinabove. By way of example, phasesn−3 and n−2 may be two different transport phases 180, and phase n−1 maybe a set-up phase 182. The fourth phase, phase n, of the sequence 190represents a suspect phase for which additional information is requiredor desired. For example, phase n of the sequence 190 may represent aboring phase 184. The boring phase 184 is typically a relatively complexphase which can include sub-phases. Due to the complexity of this phase,it may be difficult to determine with high accuracy the exact start ofthe boring phase 184. Knowing the exact start of the boring phase 184allows data acquired and computed during the boring phase 184 to beaccurately assigned to this phase. Moreover, knowing the exact start ofthe boring phase 184 allows with great certainty one or more precedingphases to be correctly identified. Having properly identified the boringphase 184, for example, the processor 101 is configured toelectronically identify one or more of the preceding phases with highaccuracy, and to correctly associate acquired data for each of thesephases with the identified preceding phases.

As a shown in FIG. 10, the state detector 164 detects a change of stateSn and, in response, the processor 101 coordinates with the userinterface 160 to generate an operator prompt 172. In some embodiments,the user interface 160 may include a display and an input device mountedon the HDD machine 105. In other embodiments, the user interface 160includes a remote device that communicates with the processor 101 (e.g.,via a wireless connection) and includes a user interface facility, suchas a locator (with a display and input device) or a tablet.

In some embodiments, the processor 101 is configured to determine withsome degree of accuracy that the suspect phase, phase n, is likely theinitiation of a boring phase 184. This initial determination by theprocessor 101 can be accomplished by analyzing communication bus trafficon the HDD machine network and/or by analyzing sensor data. The operatorprompt 172 can involve presenting a question about the identity of thepresent phase (e.g., “Is this the start of a boring phase?”) on adisplay of the user interface 160. The user interface 160 is configuredto receive a tactile or audio input 173 from the operator in response tothe prompt 172. In response to confirming that the present phase is theboring phase 184 using the operator input 173, the processor 101 enablesinitiation of the boring phase 184. It is noted that, according to someembodiments, initiation of the boring phase 184 (or other phase) islocked-out (prevented) until a confirming input 173 is received from theoperator by the user interface 160.

In response to the confirmation input 173 received from the operator,the processor 101 can correctly (with 100% accuracy based on operatorinput and contextual data) identify the current phase, phase n, andgenerates a phase identification, ID_(n), for the current phase. Havingcorrectly identified the current phase, phase n, via operator input, theprocessor 101 is configured to correctly identify one or more precedingphases, such as phases n−1, n−2, and n−3. Generally, the processor 101can make a reasonably accurate determination of the identity of thepreceding phases, based on the various information acquired during eachof the preceding phases. After the identity of phase n has beenconfirmed by the operator, the processor 101 can more accuratelydetermine the identity of the preceding phases. For example, theprocessor 101 can be configured to recognize proper and impropersequences of HDD project phases and sub-phases. Accurately knowing theidentity of a particular phase, such as phase n, allows the processor101 to eliminate from consideration those phases and sub-phases thatlogically cannot or should not occur prior to the particular phase.Although only one of the phases, phase n, in the sequence 190 is shownas requiring or desiring an operator input confirmation, more than onephase may be subject to an operator confirmation procedure in accordancewith various embodiments.

FIG. 12 illustrates various components of a system for automaticallytallying drill rods of a drill string and for automatically identifyingand acquiring data for boring phase processes performed by a drillingmachine 105 (which may be an HDD machine or other drilling machine) inaccordance with various embodiments. In the embodiment shown in FIG. 12,the system includes a controller 101, which typically includes aprocessor or other logic device. The controller 101, which is coupled tomemory 162, is configured to implement drill rod tally logic 103, inaccordance with various embodiments. The controller 101 is alsoconfigured to execute one or more algorithms for automaticallyidentifying and acquiring data for boring phase processes performed bythe drilling machine 105. The controller 101 is communicatively coupledto a drilling machine 105, a drill rod manipulation apparatus 107, and asensor system 109. The drill rod manipulation apparatus 107 isconfigured to facilitate adding and removal of drill rods respectivelyto and from a drill string comprising a multiplicity of drill rodscoupled together. The sensor system 109 includes various sensorsprovided on the drill rod manipulation apparatus 107 and the drillingmachine 105. The sensors of the sensor system 109 monitor variouscomponents of the system to determine the state of the components, fromwhich the controller 101 can coordinate rod tallying methodologies ofthe present disclosure.

In some embodiments, the drilling machine 105 shown in FIG. 12 isconfigured for horizontal directional drilling. A horizontal directionaldrilling machine, for example, is understood by those of ordinary skillin the drilling industry as a machine that provides directional drillingof relatively shallow (e.g., depths of less than about 20-30 feet) andpredominantly horizontal bores through the earth, such as for runningutilities under a roadway, for example. In other embodiments, thedrilling machine 105 shown in FIG. 12 is configured for verticaldrilling, which may include vertical directional drilling. In contrastto a horizontal directional drilling machine, a vertical drillingmachine is understood by those of ordinary skill in the drillingindustry to be a machine that provides drilling of relatively deep(e.g., hundreds or thousands of feet) and predominantly vertical boresin the earth (e.g., oil and gas wells). Although the present disclosuredescribes various rod tallying methodologies in the context ofhorizontal directional drilling, it is understood that the disclosedmethodologies may be applied in the context of vertical drillingmachines, including those with a directional (i.e., steering)capability.

Vertical drilling rigs have traditionally used a measure of the weighthanging on the rotation unit as an indication of when the drill stringis suspended. This measure of weight appears to have historically been aprimary input used to calculate drill rod length. Accordingly, verticalrigs have not relied on make-up/break-out processes to monitor the rodcount. Further, unlike horizontal directional drilling rigs, verticaldrilling machines or rigs generally include devices known as slips,which are passive devices that, once installed, limit movement of agiven drill string. This difference between vertical and horizontaldrilling rig configuration would directly impact any rod counting logic,in that a slip is an extra system element that does not interact withthe make-up/break-out processes in the same way that vises do onhorizontal directional drilling rigs.

FIG. 13 is a block diagram of various components of a system 150 foraccurately tallying drill rods added to and removed from a drill string,in accordance with various embodiments of the disclosure. The system 150is also configured for automatically identifying and acquiring data forboring phase processes performed by a drilling machine (see drillingmachines 100 and 105 shown in FIGS. 1 and 12, respectively). The system150, shown in FIG. 13, includes a controller 101, which iscommunicatively coupled to a number of components. The system 150includes a number of sensors 152 provided on a drilling machine thatmonitor various system parameters that are assessed during rod tallyingmethodologies of the present disclosure. The controller 101 iscommunicatively coupled to the rotary drive 154, such as that shown aspart of the gearbox 108 of FIG. 1. The controller 101 is alsocommunicatively coupled to a displacement drive 156 and a visearrangement 158. In some embodiments, the vise arrangement 158 includestwo independently controllable vises, such as an upper vise and a lowervise.

According to various embodiments, rod tallying methodologies areconducted fully automatically without intervention of a human operator.In some embodiments, rod tallying methodologies are conductedsemi-automatically with some intervention by a human operator. Inembodiments involving some intervention by a human operator, a userinterface 160 is communicatively coupled to the controller 101 and isused during rod tallying procedures, in accordance with variousembodiments. The system shown in FIG. 13 can be used to implementvarious rod tallying methodologies disclosed herein and in commonlyowned U.S. application Ser. No. 14/755,978, filed on Jun. 30, 2015, andU.S. Provisional Application Ser. No. 62/019,873 filed on Jul. 1, 2014,which are incorporated herein by reference.

With particular reference to FIGS. 12 and 13, the following illustrativeembodiments can be implemented by an HDD machine described previouslyhereinabove. This description assumes that it is logical to define thestarting point of a typical HDD project phase as the end of the previousphase. Thus, consideration is given to various ways that a phase willend. According to some embodiments, an important aspect of this system,as described hereinbelow, is the automatic assignment of phase [states].In the following illustrative embodiments, the project [phases] are forthe most part highlighted in [brackets] to draw attention to theimportance of these [phases]. The assumption will be that while boring,the system will be in a project phase of [boring]. To enter into the[boring] phase, the system will require that an operator confirm that aboring project has started. While in the project phase of [boring],there will be a number of sub-phases to track various metrics of theprocesses of these sub-phases, that will be described in more detailbelow. This description will start by describing various ways that theproject phase can be changed from [boring] to [breakdown start], as theHDD project is finished.

Product being installed will be pulled-back (during a pullback/reamerphase) until it is located where the crew wants it before disconnectingthe product from the puller, or the swivel from the reamer. Theassumption of this description is that a manager may want to trackactivities that occur between the time the product is first pulled backto that location and the time the HDD machine is moved away from thatphase, the process that will be referred to as the break-down process.There are a number of different ways that a bore may end, including:

-   -   1) The product may be pulled into an entry pit and disconnected        from the reamer or a drill head in the entry pit. In this        scenario, the machine may be set-back a significant distance        from the entry-pit, and the drill string may enter the ground at        an entry point, extend several rods to a desired depth and        leveled out as it enters the entry pit, where it will extend        through the entry pit before re-entering the ground. In this        scenario, it will be possible to detect when the pull-back has        ended by a number of options:        -   a. The rod count could still be as high as 3 or more rods,            so the system may utilize logic to recognize when pull-back            force is significantly lower,        -   b. or when the product is pulled-back without rotation of            the drill string, or pumping of fluid, which can only occur            after the backreamer or drill head have emerged from the            bore hole.        -   c. The system may then request operator confirmation that            the pullback has ended, even if rod count may be >0 (Note            this type of logic could be a trigger for a cross-bore            detection, or frac-out detection: if fluid pressure drops            suddenly, the system automatically asks the operator if the            pull-back is finished, and if the response is NO, then it            could be an indication of a cross-bore).        -   d. The system includes logic (e.g., fuzzy logic) at the            start of the bore, to monitor torque and rotation to            automatically log the point when the bore starts, even if            the boring does not start until after rod 1, such as after            the drill head passes through the entry pit. A relative rod            count could be automatically be set to 0 when the drill head            first starts the actual bore, where the system could            maintain both a relative rod count and an absolute rod            count. The actual bore could be defined as the bore between            either the entry point (if there is not an entry pit), or            the entry pit and the exit pit. With an entry pit the rod            count could be 3 or more to bore to a depth, when the bore            passes through the entry pit before starting the actual            bore. The system can monitor thrust, rotation, drill string            extension and fluid pressure to automatically detect an            entry pit during the pilot bore, and then automatically            request operator confirmation that the actual bore is being            started, to verify accuracy of the relative rod count. If            that has been implemented, then the system can automatically            request operator confirmation that a bore is finished            whenever the drill string is pulled back to that point.        -   e. However, the system designer may need to consider whether            additional requests for confirmation will be annoying for an            operator, and consider if it is better to sense this            automatically, considering the reliability of automatic            sensing.    -   2) The product may be pulled back to an entry point: the rod        count may or may not be at 0, as the machine may be set-back        some distance from the entry point. The same considerations        apply as for the above scenario, where the rig may know, from        what happened during the pilot shot, where the bore started, or        it could automatically assess pullback force, torque, fluid flow        and pressure to detect the end, at which time the system could        automatically generate an operator confirmation request, to        verify if the pull-back is completed, or to simply automatically        detect the end of the pullback, if it can be accomplished        reliably.

For these two scenarios, 1 and 2 defined above, that may include anautomatically generated operator prompt of [Pullback ended?] and afterthe operator provides a positive response to that prompt, or if it ispossible to reliably sense this automatically, then the status can beupdated at that time to a project phase of [break-down₀] and a timestampwill be logged. During this time, the crew will be doing a variety oftasks such as removing the product puller, pulling back the rest of thedrill string, removing the reamer, cleaning the jobsite and the drill,cleaning the tooling, etc. At some point the rack of the drill will betilted into its transport position.

While in the [break-down₀] state, it is possible to log operatingparameters and accumulate usage metrics, such as:

-   -   Rack tilt up control used along with a time stamp. This would        allow assessment of the time between finishing the pull-back,        and raising the rack. This information may be useful to monitor        if it is more efficient to raise the rack when doing some of the        processes required during break-down.    -   Engine metrics could be logged, such as amount of time engine is        running at low idle, at high idle.    -   Rod_(n) data can be logged, to log metrics for the amount of        time required to pull-back rods after the product is released.

The project phase will automatically be changed from [break-down₀] to[break-down₁] and a time stamp logged when the ground drive controls arefirst used. The ground drive controls may be utilized before many of thebreak-down tasks are completed, and tracking the use of the ground drivesystem may provide insight into how efficiently a crew is operating.

The ground drive controls could be used any number of times duringbreak-down, and each time that they are used, the project phase will bechanged to [break-down_(n)] where n=the number of times the ground drivecontrols are used while in the break-down phase. During each break-downphase it is possible to log operating parameters and accumulate usagemetrics as noted above.

When in the [break-down_(n)] state, the system will automaticallymonitor the ground drive controls, and ground drive hydraulic pressureand flow. If the ground drive is used for a predetermined amount oftime, or in a specific way, such as counter rotation, or to move apredetermined distance, then the system will assume that the break-downprocess is finished, the project phase will automatically be updated to[transport₀], and the final project manifest can be generated for theprevious project or phase.

-   -   3) There is one scenario that is a bit different: The product        may be pulled back to the entry point, but the pullback,        rotation and fluid all stopped before the reamer or drill head        is completely out of the bore, with the intention of completing        the pullback with the ground drive.        -   In this scenario, the operator will not be at the control            station, and not able to see or reply to a confirmation            request during the subsequent process. To address this            scenario, the system will automatically update the project            phase to [breakdown₀] and log a timestamp, when the ground            drive controls are first used.        -   If the system utilized logic during the pilot bore, then            this conclusion could be reached only when the system knows            the drill head, backreamer or product are at approximately            the same location as where the bore started.        -   During this phase, the operator will most likely, but not            always, tilt the rack into its transport position, and then            use the drill's ground drive system to continue pulling-in            the product. During this state, the system can log            parameters and accumulate usage metrics, such as:            -   a. Pullback max pressure, pullback duration or distance            -   b. Rack control usage along with a time stamp. This                would allow assessment of when the rack is raised or                lowered during this phase. This information may be                useful to monitor if it is more efficient to raise the                rack at a specific time.            -   c. Engine metrics could be logged, such as amount of                time engine is running at low idle, at high idle.            -   d. Rod_(n) data can be logged, to log metrics for the                amount of time required to pull-back rods while in this                state, i.e. in the event the ground drive is used to                pullback some distance, and then the carriage is used to                pull back an additional distance.        -   When in the [breakdown₀] phase, the system will be            monitoring the ground drive controls again. When in this            mode, if the ground drive controls are used again, within a            short period of time, and for a short period of time, such            as to move the drill a short distance, then the system will            assume this is just an additional ground drive pull-back,            and the system will automatically update the project phase            to [breakdown₁] with a time stamp.        -   When in a [breakdown_(n)] phase, the system will monitor the            way that the ground drive controls are used to identify when            the breakdown phase is finished, such as if the ground drive            is used for a predetermined amount of time, or in a specific            way, such as counter rotation, or to move a predetermined            distance, then the system will assume that the break-down            process is finished, the project phase will automatically be            updated to [transport₀], and the final manifest can be            generated for the previous project or phase.

Once the project phase is set to [transport₀], in either scenario, theprevious phase will be assumed to be finished and the next phasestarted. While in transport mode, the system may be set-up to monitorand record various parameters, including:

-   -   Maximum ground drive pressure, that may be an indication of how        the machine is being operated during transport;    -   Accumulated time during that state that the engine is running;    -   Etc.

When in the [transport_(n)] phase, the system will monitor the rack tiltcontrol to divide parameters into separate phases. While in transport,the rack will normally be tilted up while the machine is moving.However, when the machine is moved onto a trailer, the rack is normallylowered, thus the change in the rack position can be an indication ofwhen the machine is on a trailer. Once the machine arrives at a jobsite,the rack will then be tilted up in order to move the machine to thelocation of set-up for the next phase. Once in the set-up position, therack will be lowered and the bore started. Thus, the last instance oflowering the rack, before a new bore is confirmed to a have started, isthe time that jobsite set-up started.

In a common scenario, the rig state will be automatically set to[transport₀], with a time stamp corresponding to when the previous phaseended. This time will be defined as corresponding to when the next phasestarts. When the machine is loaded onto a trailer, and the rack tilteddown, state will be updated to [transport₁] and a time stamp willautomatically be logged. Various other metrics can be tracked duringthese various states, including engine running duration, engine averagerpm, etc.

When the machine arrives at the jobsite, on the trailer, the rack willbe tilted back to transport, and the system will then automaticallychange the state to [transport₃] with a time stamp. Once the machine isput into position to start the next project, the rack may be lowered,and the system will automatically update the state to [track₄] with atime stamp. It is possible that the rig is not in the exactly correctposition, so the process of tilting the rack and moving the machinecould be repeated any number of times. Each of these movements,repositionings, will result in additional project status events of[track_(n)] each with a unique time stamp, and with a unique record ofother parameters. Once an actual bore is started, and the drill rodtally changes from 1 to 2, then the system will generate an operatorconfirmation request, to verify that a bore has started. Once thatconfirmation is received, then the system will process the previouslylogged [transport_(n)] state to save that record as a summary of theset-up phase.

Embodiments of the disclosure include an algorithm that assesses variousmachine parameters and automatically assigns a machine phase (e.g.,phase ID) for a set of related HDD machine processes. The HDD machinephases can include, for example, Stationary Transport, Moving Transport(under remote control), Moving Transport(under on-rig control), TrailerTransport, Set-up stationary, Set-up moving (under remote control),Set-up moving (under on-rig control), Pilot Bore rod_(n) start, PilotBore rod_(n) end, Pullback rod_(n) start, and Pullback rod_(n) end.

According to some embodiments, when the HDD machine phase transitionsfrom one phase to another, the algorithm stores data for the phase to atemporary cache of memory, along with a time stamp indicating the timethat the new phase was detected. When the HDD machine phase changes from(pilot bore rod₁ end) to (pilot bore rod₂ start), for example, thealgorithm requests confirmation from the operator that a pilot bore hasstarted. Once that confirmation is received, the algorithm initiatesactions for that specific phase including the following:

-   -   1) generates an automatically assigned phase ID code and queries        the operator for a custom phase code;    -   2) creates a digital summary report or manifest for that        specific phase;    -   3) queries the data log cache to calculate attributes of        productivity for that specific phase that have already occurred        including:        -   a. calculating (transport time), and saving a machine            transport report to this record including recording machine            attributes that occurred while the machine was in transport            state including maximum ground drive pressure, average            ground drive pressure;        -   b. calculating (set-up time);        -   c. calculating (rod 1 time) and saving a rod 1 report to            this record including recording machine attributes that            occurred while the machine was in rod 1 state including            maximum rotation pressure, average rotation pressure,            maximum thrust pressure, average thrust pressure;        -   d. calculating (add rod 2 time); and        -   e. after the calculations are completed, and data is written            to the digital summary report, the data log cache is            updated, to clear-out data points that will not be needed            for future calculations.            As the bore progresses and each time the status changes from            a (rod_(n) end) to the subsequent (rod_(n+1) start), the            algorithm automatically queries the data log cache to            calculate the just-finished rod time, and also stores the            recorded machine attributes for that rod, to the digital            summary report.

The above-described process allows for situations where a trip-out mayoccur during a pilot bore by including logic wherein if the rod countdecrements more than 1 rod, the system automatically queries theoperator asking for confirmation that pullback has started. If theoperator's response is no, then the data is logged as a trip-out. Forexample, one pilot rod may have a rod time of 30 sec during the initialbore, 10 sec during trip-out and then 10 sec during the subsequenttrip-in. Once the pilot bore is finished, the rod count decrements morethan one rod, and the operator confirms that a pull-back has started,then the algorithm will query the data-log to assign time metrics to atooling change-over process, and the subsequent rod by rod data will betracked as pull-back data.

Pullback can have several variations including the simplest form where adrill string is formed during a pilot bore, and then that drill stringis pulled-back during a pull-back during which the bore hole is expandedand product is pulled-in. More complicated bores include variationsincluding:

-   -   Forming a reamer string, where-in a section of the drill string        can be pushed-out beyond the exit extending the same distance as        the length of the bore. Once pushed out beyond the exit pit, the        reamer string is disconnected from the drill string, a reamer        installed on the drill string, the reamer string attached to the        other side of the reamer, and pulled into the bore hole along        with the reamer. The drill string is then attached to the reamer        string when the reamer is pulled back to the entry pit, and a        second reamer is then attached to the reamer string and it is        pulled back.    -   Push reaming.    -   Trailing rod—related to the reamer string noted above.

Additional complications can occur during the transition from the pilotbore to a subsequent process, including the possibility that extra rodcould be pushed-out through the exit pit to make it easier to changetooling, so it may be difficult to detect the actual length of the boredhole, by a knowledge of the number of rods in a drill string. Some ofthis complexity can be managed by periodically requesting input from theoperator.

In addition to caching timestamp data, the system can cache machineparameters such as hydraulic pressures that correlate to rotationaltorque applied to the drill string or to longitudinal force applied tothe drill string, for instance. These other datasets can be evaluated toderive other information that can be related to a specific process.

The discussion and illustrations provided herein are presented in anexemplary format, wherein selected embodiments are described andillustrated to present the various aspects of the present invention.Systems, devices, or methods according to the present invention mayinclude one or more of the features, structures, methods, orcombinations thereof described herein. For example, a device or systemmay be implemented to include one or more of the advantageous featuresand/or processes described below. A device or system according to thepresent invention may be implemented to include multiple features and/oraspects illustrated and/or discussed in separate examples and/orillustrations. It is intended that such a device or system need notinclude all of the features described herein, but may be implemented toinclude selected features that provide for useful structures, systems,and/or functionality.

Although only examples of certain functions may be described as beingperformed by circuitry for the sake of brevity, any of the functions,methods, and techniques can be performed using circuitry and methodsdescribed herein, as would be understood by one of ordinary skill in theart.

What is claimed is:
 1. A method for use by a drilling machine,comprising: receiving drilling machine data during execution a pluralityof processes by the drilling machine associated with each of a pluralityof phases of a drilling project; automatically detecting a start stateand an end state of each of the phases; generating time stamp data inresponse to detecting at least the start state of each phase; receivingan operator input confirming the start state of a particular phase ofthe plurality of phases; electronically identifying the particular phaseand one or more phases preceding the particular phase based on theoperator input; storing the identity, a time duration, and the machinedata for each of the particular and preceding phases; and generating anoutput comprising the identity, a time duration, and the machine datafor each of the phases.
 2. The method of claim 1, wherein receiving theoperator input comprises displaying a prompt for the operator input on adisplay coupled to the drilling machine.
 3. The method of claim 1,further comprising: deriving attributes for each of the phases using oneor both of the time stamp data and the machine data for each phase; andstoring the derived attributes for each of the phases; wherein thegenerated output further comprises the derived attributes for each ofthe phases.
 4. The method of claim 1, wherein the time stamp data foreach phase comprises: a start time stamp and an end time stamp; or astart time stamp and an end time stamp defined by a start time stamp ofa successive phase; or an end time stamp and a start time stamp definedby an end time stamp of the preceding phase.
 5. The method of claim 1,wherein: the machine data and the time stamp data for each phase arestored in a temporary memory cache after detecting the start state ofeach phase; and the method further comprises transferring the machinedata and the time stamp data from the temporary memory cache to archivememory in response to detecting the end state of each phase.
 6. Themethod of claim 5, wherein the archive memory is configured to define aproject manifest organized by phase with each phase associated with itsrespective machine data and time stamp data.
 7. The method of claim 1,wherein the machine data comprises at least some of maximum ground drivepressure, average ground drive pressure, maximum rotation pump pressure,average rotation pump pressure, maximum thrust pump pressure, andaverage thrust pump pressure.
 8. The method of claim 1, wherein theparticular phase comprises a stationary transport phase, a movingtransport phase, a trailer transport phase, a set-up stationary phase,or a set-up moving phase.
 9. The method of claim 1, wherein theparticular phase comprises a set-up phase and the phase preceding theset-up phase comprises a transport phase.
 10. The method of claim 1,wherein: the particular phase comprises a boring phase and the phasepreceding the boring phase comprises a set-up phase; or the particularphase comprises a boring phase and the phase preceding the boring phasecomprises a transport phase; or the particular phase comprises apullback or reaming phase and the phase preceding the pullback orreaming phase comprises a boring phase; or the particular phasecomprises a breakdown phase and the phase preceding the breakdown phasecomprises a boring phase; or the particular phase comprises a breakdownphase and the phase preceding the breakdown phase comprises a pullbackor reaming phase.
 11. The method of claim 1, wherein: the particularphase and the one or more preceding phases define sub-phases of the samedrilling project phase; and electronically identifying the particularphase comprises electronically identifying all sub-phases of theparticular phase and the one or more preceding phases.
 12. The method ofclaim 1, wherein: the particular phase and the one or more precedingphases define sub-phases of a boring phase, a pullback phase or areaming phase; and one or more of the sub-phases involves the additionor removal of a drill rod respectively to or from a drill string coupledto the drilling machine.
 13. A method for use with a drilling machine,comprising: receiving data about the drilling machine during a pluralityof processes associated with each of a plurality of non-excavationphases of a drilling project; automatically detecting a start state andan end state of each of the phases; generating time stamp data inresponse to detecting at least the start state of each phase; receivingan operator input confirming the start state of a particular phase ofthe plurality of phases; electronically identifying the particular phasebased on the operator input; storing the identity, a time duration, andthe machine data for the particular phase; and generating an outputcomprising the identity, time duration, and machine data for theparticular phase.
 14. The method of claim 13, wherein electronicallyidentifying the particular phase comprising electronically identifyingthe particular phase and one or more phases preceding the particularphase based on the operator input.
 15. An apparatus for use with adrilling machine, the apparatus comprising: a processor; a memory; atimer device; a state detector; and a user interface; wherein theprocessor is configured to: receive drilling machine data duringexecution of each of a plurality of phases of a drilling project;cooperate with the state detector to automatically detect a start stateand an end state of each of the phases; cooperate with the timer deviceto determine a time duration of each phase; cooperate with the userinterface to receive an operator input confirming the start state of aparticular phase of the plurality of phases; electronically identify theparticular phase and one or more phases preceding the particular phasebased on the operator input; store the identity, a time duration, andthe machine data for each of the particular and preceding phases in thememory; and generate an output comprising the identity, a time duration,and the machine data for each of the phases.
 16. The apparatus of claim15, wherein: the user interface comprise a display and an input device;and the processor is configured to cooperate with the user interface todisplay a prompt for the operator input on the display.
 17. Theapparatus of claim 15, wherein the processor is further configured to:derive attributes for each of the phases using one or both of the timestamp data and the machine data for each phase; and store the derivedattributes for each of the phases in the memory; wherein the generatedoutput further comprises the derived attributes for each of the phases.18. The apparatus of claim 15, wherein the memory is configured todefine a project manifest organized by phase with each phase associatedwith its respective machine data and time stamp data.
 19. The apparatusof claim 15, wherein: the particular phase and the one or more precedingphases define sub-phases of a boring phase, a pullback phase or areaming phase; and one or more of the sub-phases involves the additionor removal of a drill rod respectively to or from a drill string coupledto the drilling machine.
 20. The apparatus of claim 15, wherein at leastsome of the phases define non-excavation phases of a drilling project.